This page last changed on Apr 27, 2006 by rossmason.

This page contains a list of known Provider Transports for Mule. If you have written a provider for mule and would like to submit it to the project, please contact us. If you only think of writing a provider, look no further than at Writing Mule Transport Providers.

For introduction to providers see Mule Endpoints and for more information about configuration of transports in Mule see Configuring Endpoints.

See General Transport Configuration for information about how Transports are configured at runtime.

Take a look at the Transports Feature Matrix.

Mule Core Providers

AS400 DQ Provider Connectivity to IBM AS400 Data Queue messaging server.
Ejb Provider Allows Ejb invocations to be made using outbound endpoints.
Email Provider This Provider supplies various email connectivity options.
File Provider This connector allows files to be read and written to directories on the local file system. The connector can be configured to filter the file it reads and the way files are written, such as whether binary output is used or the file is appended to.
Ftp Provider Allows files to be read / written to a remote ftp server.
Http Provider This provider supplies Http and Https transport of mule events between applications and other Mule servers.
Imap Provider Connectivity to Imap mail folders including IMAPs (secure) support.
Jdbc Provider A Mule provider for Jdbc Connectivity.
Jms Provider A Mule provider for Jms Connectivity. Mules itself is not a Jms server but can use the services of any Jms 1.1 or 1.02b compliant server such as ActiveMq, OpenJms, Joram, JBossMQ and commercial vendors such as WeblogicMQ, WebspereMQ, SonicMQ, SeeBeyond, etc.
Multicast Provider Allows your components to receive an send events via IP multicast groups.
Pop3 Provider Connectivity to POP3 inboxes including POP3s (secure) support.
Quartz Provider Provides scheduling facilities with cron / interval definitions and allows Mule events to be sheduled/rescheduled.
Rmi Provider Enables event to be sent and received over rmi via jrmp.
Servlet Provider Provides connectivity to the Mule server via servlets. provides facilities for Mule components to listen for events received via a servlet request. There is also a servlet implementation that uses the Servlet provider to enable REST style services access. Note this transport is now bundled with the Http transport.
Smtp Provider Connectivity to Smtp servers including SMTPs (secure) support.
Soap Provider Enables your components to be exposed as web services and to act as soap clients. The Soap provider supports Web Methods Glue and Apache Axis.
Ssl Provider Provides secure socket-based communication using SSL or TLS.
Stream Provider This provider allows connectivity to Streams such as System.in and System.out and is useful for testing.
Tcp Provider Enables events to be sent and received over tcp sockets.
Udp Provider Enables events to be sent and received as datagram packets.
Vfs Provider Enables access to and from various protocols such as WebDav, Samba, File System, Jar/Zip and more. This transport is currently in the Sandbox.
Vm Provider A Mule provider that enables event sending and receiving over VM or embedded memory or persistent queues.
WSDL Provider The WSDL transport provider can be used to for invoking remote web services by obtaining the service WSDL. Mule will create a dynamic proxy for the service then invoke it.
Xmpp Provider A Mule provider for connectivity over Xmpp (Jabber) instant messaging protocol
Document generated by Confluence on Nov 27, 2006 10:27